Hello,

We have 2013 Exchange consisting of 2 CASs and 2 MBX servers spanning two locations via VPN, 1 of each server in each location. We are hosting exchange for an outside domain, and have just transferred them into our organization within the last month. There are two users who consistently have messages stuck in the "Retry" status in the submission queue. Not all of their messages, but usually 2-4 are stuck and eventually kicked back to them. 

I have read other forums about a potential issue with conversion to RTF. I have forced the queues empty and attempted this fix, but within a week the users had messages stuck again.

Has anybody run into this and possibly found a fix?

Hi

If you restart the transport service does it flush the queue? Any AV on the box?

What errors are logged in event viewer? what are the errors in the queue?

Hi,

Most of the times when messages get stuck in the submission queue it's due to third party apps or event sinks that process the message before it's given to the transport mechanism.

Can you try disabling your AV\SPAM stuff, restart SMTP and possibly your Exchange services, transport server to test.

In addition,as Dare mentioned, Are there any logs ?

Thanks.

1.  Recreated user's Outlook profile from scratch

2.  Started Outlook in Safe Mode

3.  Removed Office 2010 installation and installed a fresh copy

4.  Changed Outlook from Cached Mode to Online

satendra

• Edited by Satendra Thursday, January 09, 2014 9:48 AM
• Proposed as answer by kyriazisg Friday, October 24, 2014 7:28 AM

Thanks for the quick replies.

Restarting the transport service did not clear the queue. No AV on this server (Mailbox Server).

Last Error:  A storage transient failure has occurred during content conversion.

And I see this in my event log but I'm not sure it's related:

Faulting application name: w3wp.exe, version: 8.0.9200.16384, time stamp: 0x50108835
Faulting module name: wsmsvc.dll, version: 6.2.9200.16384, time stamp: 0x50108617
Exception code: 0xc0000005
Fault offset: 0x000000000009859a
Faulting process id: 0x16764
Faulting application start time: 0x01cf0e2796adcdf2
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\wsmsvc.dll
Report Id: b7b5d3cd-7a2d-11e3-940b-000c2917d040
Faulting package full name:
Faulting package-relative application ID:

The queue is holding on 1 of my mailbox servers. Which server would i restart it on? just the mailbox server?

Hi,

Did you try Satendra's suggestions above?

In addition, I recommend you try the following methods:

1.Move these users to another database and check the result.

2.Recreate the mailbox and check the result.

Thanks.

Thank you for all your replies.

It appears this issue has been resolved. At first I made the following change:

Get-RemoteDomain | Set-RemoteDomain -TNEFEnabled $False

Restarted Transport services on both mailbox DB Servers and the messages remained in the queue and more messages were getting stuck.

Then I made this change:

Get-RemoteDomain | Set-RemoteDomain -TNEFEnabled $True

Restarted Transport services on both mailbox DB Servers and the messages cleared from the queues and it seems no more messages are getting stuck as they were before.

I also changed the message timeout from 2 days to 2 hours. I'd rather know sooner than later that a message was stuck. I plan to continue monitoring this.

Thanks again.

• Marked as answer by SteveGlobalIT Tuesday, January 14, 2014 6:23 PM

I have a problem with this answer, yes it helps to gets your email trough the submission queue.... BUT it is sending all the emails like winmail.dat or filter all the attachments.
This problem started with no reason at all and everytime we set the TNEFEnabled to true to get the mails out the submission, but quickly set it to false because we get all the calls from receivers they get no attachment or an winmail.dat.
OK we can say, let them install a winmail.dat tool... NO way we tell to 10.000+ customers to install a tool because we have a crappy Exchange.
It is not the case some people have problems, no.... all the people have the same problem. There is no answer on the internet that provide the real solution, maybe the solution is not using Exchange anymore? PLEASE give us a solution that works, not a workaround with many problems.
Don't come with solutions like Outlook without cache, safe mode etc. That is not the solution and is eating precious time to get to the real solution. Our Outlook is running without cache for many years, there where no changes made to any product.
We have Exchange 2013 CU3 with all the updates there are, we need help with this, wo can provide us with the correct solution?

Thank you for all your replies.

It appears this issue has been resolved. At first I made the following change:

Get-RemoteDomain | Set-RemoteDomain -TNEFEnabled $False

Restarted Transport services on both mailbox DB Servers and the messages remained in the queue and more messages were getting stuck.

Then I made this change:

Get-RemoteDomain | Set-RemoteDomain -TNEFEnabled $True

Restarted Transport services on both mailbox DB Servers and the messages cleared from the queues and it seems no more messages are getting stuck as they were before.

I also changed the message timeout from 2 days to 2 hours. I'd rather know sooner than later that a message was stuck. I plan to continue monitoring this.

Thanks again.

Stop Stop Stop, this isn't a solution! Every single post I run into this answer, but it is a real crappy "solution". Simple: there is no solution yet, if everyone take this for an answer there will never we a good answer! This is a work around, we got mails stucked in the queue for 2 months and it start with no reason. We have every update, enough disk space etc. Settinf the remote domain to true brings you the problem with Apple users and Gmail, hotmail etc. They will receive an email.dat or no attachment when you send HTML mail. The False or Null is a future that make mail HTML so you can use signatures, pictures etc. It always worked, now only for 2 days and we must reboot again. Set de Remote domain to true we have problems with customers who doens't receive their email correct!.

Microsoft please solve this problem and stop making crappy excuses or crappy workarounds, a solution is what we need!!!

• Edited by helpdeskwest Wednesday, July 09, 2014 8:14 AM

Well, just to pose my problem...

Have a single Exchange 2013 Server, and just started to use Sonian Archiving for backup. Recently several emails were sent that exceed the maximum size that Sonian accepts. The Archiving process is achieved through journaling.

These several emails stuck "retrying" to submit to Sonian. How can I clear these emails. I've already adjusted the mail limits to prevent this in the future, but how can I clear these emails?

Thanks in Advance.